fix: Adding a hardcoded createdBy parameter to the deploy.yml file to prevent validation pipeline failures caused by the deployer function in the Bicep file. #448
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Purpose
This pull request introduces a small but important improvement to how resource tags are set during deployment. The main change is to make the "CreatedBy" tag more flexible and allow it to be set via a parameter, rather than always deriving it from the deployer’s principal name.
Tagging improvements:
createdByparameter toinfra/main.bicep, allowing the "CreatedBy" tag to be explicitly set or default to the deployer's username if not provided..github/workflows/deploy.ymlto pass acreatedBy="Pipeline"value when running deployments, ensuring resources created by the pipeline are tagged accordingly.Does this introduce a breaking change?
How to Test
What to Check
Verify that the following are valid
Other Information